home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: netcom.com!jtessin
- From: jtessin@netcom.com (John Tessin)
- Subject: Re: TCP/IP in Windows
- Message-ID: <jtessinDMBDD6.IGA@netcom.com>
- Organization: NETCOM On-line Communication Services (408 261-4700 guest)
- X-Newsreader: TIN [version 1.2 PL1]
- References: <4eh5i2$3a8@news.axess.com>
- Date: Mon, 5 Feb 1996 17:46:18 GMT
- Sender: jtessin@netcom21.netcom.com
-
- Mark Santelli (marks@axess.com) wrote:
- : Does anyone know what functions are availible to do TCP/IP
- : communications in Windows. I've done stream socket programming
- : in a UNIX environment using functions like socket(), listen(),
- : accept(), etc. I use Borland's C++ 4.52 and can't seem to get
- : any help on the subject. How does one write internet and
- : communication based code in Windows programming.
-
- The sockets API for windows is called WINSOCK. The standard Berkely
- sockets are supported, for the most part, along with calls that are
- designed to integrate well with the messaging paradigm of Windows.
- The spec is available on the net, I downloaded it myself. Just do a
- search with the keyword Winsock.
-
- BTW - I don't know about Win95, but if you use NT you can use threads to
- handle individual sockets with the blocking attribute, although
- allocating a pool of threads to handle a linked list of sockets is more
- efficient. (NT is also POSIX compliant.)
- --
- jtessin@netcom.com
- CIS: 71774,1731
-
- ===============================================================
- If ye love wealth better than liberty, the tranquility of
- servitude better than the animating contest of freedom, go
- home from us in peace. We seek not your counsels or arms.
- Crouch down and lick the hands which feed you. May your
- chains set lightly upon you, and may posterity forget
- that ye were our countrymen." -- Samuel Adams
- ===============================================================
-